SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 42329: The Replacement node Extreme Percentiles results might be incorrect if a Frequency variable is used

DetailsAboutRate It

If you you specify the Extreme Percentiles Default Limits Method in the SAS® Enterprise Miner™ Replacement node, and if your data contains a variable with a frequency role, then the results of the node might be incorrect.

There are no errors or warnings to indicate that a problem occurred.

To work around the problem, do not use a frequency role. Instead, "expand" your data.

Example

Suppose that you want the Extreme Percentiles method, but your data set contains a variable called MY_FREQ_VARIABLE that you are using in a frequency role.

Delete the connection between your Replacement node and the predecessor node that contains the training data with frequency variable. Insert a SAS Code node in your path immediately before the Replacement node. Connect your predecessor node to the SAS Code node. Enter the following code using the Code Editor:

data &em_export_train;
   set &em_import_data;
   do my_temp_variable=1 to int(my_freq_variable);
      output;
      end;
   drop my_temp_variable my_freq_variable;
   run;

Close the SAS Code node, and run it. The code will expand the data by repeating each observation according to the value of the MY_FREQ_VARIABLE variable.

Connect the SAS Code node to your Replacement node, and run the Replacement node. The Replacement node will not use the variable MY_FREQ_VARIABLE as a frequency role because the SAS Code node dropped the variable. The Replacement node will use the correct number of observations because the SAS Code node created an expanded data set that does not need the frequency variable.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise Minerz/OS5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows XP 64-bit Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows 2000 Advanced Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Server5.39.1 TS1M3 SP4
Microsoft Windows 2000 Professional5.39.1 TS1M3 SP4
Microsoft Windows NT Workstation5.39.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Standard Edition5.37.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows XP Professional5.37.19.1 TS1M3 SP49.3 TS1M0
Windows Vista5.37.19.1 TS1M3 SP49.3 TS1M0
Windows Vista for x645.37.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled AIX5.37.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled HP-UX5.37.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled Solaris5.37.19.1 TS1M3 SP49.3 TS1M0
HP-UX IPF5.37.19.1 TS1M3 SP49.3 TS1M0
Linux5.37.19.1 TS1M3 SP49.3 TS1M0
Linux on Itanium5.37.19.1 TS1M3 SP49.3 TS1M0
Solaris for x645.37.19.1 TS1M3 SP49.3 TS1M0
Tru64 UNIX5.37.19.1 TS1M3 SP49.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.